home *** CD-ROM | disk | FTP | other *** search
- RAMScrap
- ========
-
- !RAMScrap is a replacement for !Scrap.
-
- Why would !Scrap need a replacement?
- ------------------------------------
-
- If the user does not have write access to !Scrap it will not work
- properly. !RAMScrap creates a scrap directory on the RAM disk so the
- user is guaranteed to have write access. Additional advantages of a
- scrap directory on the RAM disk are there will be no disk swopping and
- it will be very fast.
-
-
- What does RAMScrap do?
- ----------------------
-
- !RAMScrap will try to create a RAM disk if one does not exist. If
- there is a RAM disk RAMScrap will check that there is enough free
- space, and if necessary and possible it will extend the RAM disk. Lots
- of things can go wrong, RAMScrap will try to do the sensible thing. If
- !RAMScrap thinks it has succeeded it sets Wimp$Scrap and
- Wimp$ScrapDir, if it thinks it has failed it tries to give the user
- helpful advice.
-
- Operation
- ---------
-
- !Boot will try to create a RAM scrap directory if one has not already
- been set (by a standard !Scrap application). !Run will always try to
- create a RAM scrap directory.
-
- !Boot and !Run use a BASIC program 'RAMDisk' to check/create/extend
- the RAM Disk. There are two variables used by 'RAMDisk' which you may
- want to adjust. They are both set within the first few lines of the
- program.
-
- required_size% : If RAMDisk creates a RAM disk it will attempt to make
- its size required_size% (K). If the RAM disk is smaller than
- required_size% RAMDisk will try to extend it. Allow for a bit of
- memory overhead, 128K of RAM disk only has 124K of user space and any
- directory structure will eat a bit more.
-
- running_commentary% : This is set to TRUE or FALSE. It is a debugging
- aid, most users will keep it set to FALSE. Set it to TRUE if you want
- a running commentary of all that RAMDisk is doing/trying to do. The
- RISC OS 2 or 3 version does not use this variable, just a lot of
- (possibly REMed out) calls to PROCout.
-
- MemAlloc
- --------
-
- The RISC OS 3 version of RAMDisk calls SWI 'ChangeDynamicArea'. RISC
- OS 2 does not have'ChangeDynamicArea' so the 'MemAlloc' module must be
- used for this version.
-
- How can the user fail to have write access to !Scrap?
- -----------------------------------------------------
-
- Some Networks have a 'public' identity which allows anyone to log on
- and access certain applications and files. Typical public IDs are
- GUEST, BOOT and (my favourite) FRED. A public ID is not usually given
- write access to any area of the network. (I have heard networks with a
- public ID described as 'open access systems').
-
- Our network at Portsmouth College allows users to log on with a public
- ID (sorry, can't bring myself to call it an 'open access system' - too
- pretentious). Imagine our distress when we found that the RISC OS 3
- printer driver required a !Scrap directory. !RAMScrap is my solution -
- hope you find it useful.
-
-
- Robert Chrismas : 19930722
-
-